The deployment follow loop returned as soon as the log stream closed,
skipping the duplicate-suppressed catch-up search whenever the stream
ended (EOF) before the poller observed a terminal status. Keep polling
after a clean stream shutdown and check terminal status immediately so
the catch-up search still runs without waiting for the next poll.

The runtime --follow loop ended as soon as the SSE stream closed, so a
dropped connection (load-balancer cap, redeploy, network blip) silently
stopped the tail even though the backend supports resuming. Reconnect
from the last stream cursor (Last-Event-ID) until the context is
canceled, relying on the server's overlap window and seen-set dedup to
avoid replaying recent events.

Deployment (build) follow is unchanged: its terminal poll and
duplicate-suppressed catch-up search already recover logs missed during
a disconnect.